Method and device for facilitating delivery of content in a multi-access edge computing (MEC) environment

ABSTRACT

An edge device may obtain, via a base station, one or more respective requests from one or more user devices to access content. The edge device may determine a total number of the one or more user devices and may determine that the total number of the one or more user devices satisfies a threshold. The edge device may determine, based on the total number of the one or more user devices satisfying the threshold, a latency requirement associated with the content and may determine whether the edge device can satisfy the latency requirement. The edge device may selectively cause, based on determining whether the edge device can satisfy the latency requirement, the edge device or a different edge device to send the content to the one or more user devices via the base station.

BACKGROUND

In a multi-access edge computing (MEC) environment, computing is enabledby a network architecture that provides computing capabilities, to auser device, via computing devices at or near an edge of a network(e.g., a wireless communication network). Accordingly, because a MECenvironment may provide computing at or near the edge of the network,increased performance may be achieved over networks that may betopologically and/or physically farther or outside the providers networkfrom a user device than a MEC environment. Such increased performancemay be achieved in the MEC environment due to less traffic and/orcongestion between a user device and the computing platform, lesslatency (due to the closer proximity), increased flexibility (due to agreater amount of computing platforms), resource availability, and/orthe like.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1J are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a flow chart of an example process for facilitating deliveryof multicast or broadcast content in a multi-access edge computing (MEC)environment.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

In some instances, one or more user devices may request access tomulticast or broadcast content (e.g., content) from a cloud environment.The cloud environment may be a multi-access edge computing (MEC)environment that includes multiple cloud levels, such as central cloud,an edge cloud, and a far edge cloud. In many cases, content may behosted by MEC devices associated with the far edge cloud and/or the edgecloud to reduce latency associated with delivering the content to theone or more user devices. However, some types of content are not aslatency sensitive (e.g., streaming video) as other types of content(e.g., augmented reality (AR) applications and/or virtual reality (VR)applications). So, utilizing far edge cloud and/or edge cloud resourcesfor less latency sensitive types of content may be an inefficient use ofresources.

Some implementations described herein provide an edge device (e.g., aMEC device) that determines which edge device, of multiple edge devices,is an optimal edge device to deliver multicast or broadcast content toone or more user devices. In some implementations, the edge deviceobtains, via a base station, one or more respective requests from one ormore user devices to access the content. In some implementations, theedge device determines a total number of the one or more user devicesand determines that the total number of the one or more user devicessatisfies a threshold. In some implementations, the edge devicedetermines, based on the total number of the one or more user devicessatisfying the threshold, a latency requirement associated with thecontent and determines whether the edge device can satisfy the latencyrequirement. In some implementations, the edge device may selectivelycause, based on determining whether the edge device can satisfy thelatency requirement, the edge device or a different edge device to sendthe content to the one or more user devices via the base station.

In this way, the edge device optimizes the use of cloud resources byensuring that the edge device that can satisfy the latency requirementfor delivering the content to the one or more user devices hosts thecontent. For example, some implementations described herein minimizeunnecessary usage of resources associated with the far edge cloud and/orthe edge cloud (e.g., because the content does not have a low latencyrequirement). As another example, some implementations described hereinfacilitate more efficient usage of cloud resources by enabling a MECdevice to send the content as a multicast and/or broadcast transmissionrather than as multiple unicast transmissions. Further, the MECenvironment can be latency sensitive for delivering multicast orbroadcast content to the one or more user devices. This enables the MECenvironment to be structured in a way to allocate resources to the faredge cloud, the edge cloud, and/or the central cloud according topractical latency requirements associated with transmitting content,which can further optimize use of cloud resources.

FIGS. 1A-1J are diagrams of an example implementation 100 describedherein. Example implementation 100 may include one or more user devices(e.g., shown as one or more user devices A and one or more user devicesB in FIG. 1A), one or more base stations (e.g., shown as base station Aand base station B in FIG. 1A), and/or one or more multi-access edgecomputing (MEC) devices (e.g., shown as MEC device A, MEC device B, MECdevice C, and MEC device D in FIG. 1A). As shown in FIG. 1A, exampleimplementation 100 may include one or more far edge clouds (shown inFIG. 1A as far edge cloud A and far edge cloud B), an edge cloud, and/ora central cloud. Far edge cloud A, far edge cloud B, the edge cloud, andthe central cloud may be part of and/or associated with a wirelesscommunication network, such as a third generation (3G) network, a longterm evolution (LTE) network, a fifth generation (5G) network, and/orthe like.

A cloud may represent a computing environment where a MEC deviceassociated with the cloud may provide services (e.g., deployapplications, store and process content, and or the like) for one ormore user devices. A cloud may provide services to one or more userdevices within an area (e.g., a physical service area of one or morebase stations and an associated MEC device). For example, a far edgecloud may provide services to one or more user devices associated with asingle base station and a MEC device (e.g., where the base station andthe MEC device are physically near each other to reduce latencyassociated with providing services). As shown in FIG. 1A, far edge cloudA may provide services to one or more user devices A associated withbase station A and MEC device A (e.g., where the base station A and MECdevice A are physically near each other). As further shown in FIG. 1B,far edge cloud B may provide services to one or more user devices Bassociated with base station B and MEC device B (e.g., where the basestation B and MEC device B are physically near each other).

As another example, a central cloud may provide services to one or moreuser devices associated with one or more base stations and a MEC device(e.g., where the one or more base stations and the MEC device arephysically far from each other). A central cloud may have a higherlatency associated with providing services than a far edge cloud, butmay have more resources (e.g., computational resources) to handleproviding the services. As shown in FIG. 1A, the central cloud mayprovide services to one or more user devices A and B associated withbase stations A and B and MEC device D (e.g., where the base stations Aand B and MEC device D are physically far from each other).

In another example, an edge cloud may provide services to one or moreuser devices associated with one or more base stations and a MEC device(e.g., where the one or more base stations and the MEC device arephysically farther from each other than in a far edge cloud but closerto each other than in central cloud). An edge cloud may have a higherlatency associated with providing services than a far edge cloud, but alower latency than a central cloud. As shown in FIG. 1A, the edge cloudmay provide services to one or more user devices A and B associated withbase stations A and B and MEC device C (e.g., where a physical distancebetween base station A and MEC device C is greater than a physicaldistance between base station A and MEC device A and less than aphysical distance between base station A and MEC device D and/or aphysical distance between base station B and MEC device C is greaterthan a physical distance between base station B and MEC device B andless than a physical distance between base station B and MEC device D).

Accordingly, base station A and/or MEC device A may be associated withfar edge cloud A; base station B and/or MEC device B may be associatedwith far edge cloud B; base station A, base station B, and/or MEC deviceC may be associated with the edge cloud; base station A, base station B,and/or MEC device D may be associated with the central cloud; and/or thelike. Further, base station A may be associated with MEC device A, MECdevice C, MEC device D, and/or the like (e.g., base station A maydirectly communicate with MEC device A via far edge cloud A, MEC deviceC via the edge cloud, MEC device D via the central cloud, and/or thelike). Base station B may be associated with MEC device B, MEC device C,MEC device D, and/or the like (e.g., base station B may directlycommunicate with MEC device B via far edge cloud B, MEC device C via theedge cloud, MEC device D via the central cloud, and/or the like).

In some implementations, the one or more user devices A may communicatewith MEC device A, MEC device C, and/or MEC device D via base station A.The one or more user devices B may communicate with MEC device B, MECdevice C, and/or MEC device D via base station B.

As shown in FIG. 1B and by reference number 102, the one or more userdevices A may request access to content. For example, each user deviceof the one or more user devices A may send a request to access thecontent to MEC device A via base station A. In some implementations, MECdevice A may obtain one or more respective requests from the one or moreuser devices A to access the content via base station A. The content maybe multicast content or broadcast content (e.g., content to be deliveredto one or more user devices simultaneously, such as a live videostreaming of a sporting event, a public safety message, and/or thelike). The content may be time synchronized content (e.g., content to bedelivered in a time synchronized manner (e.g., with minimal to nolatency) to one or more user devices (e.g., for augmented reality (AR)applications, virtual reality (VR) applications, and/or the like).

As shown by reference number 104, the one or more user devices B mayrequest access to the content in a similar manner as the one or moreuser devices A. For example, each user device of the one or more userdevices B may send a request to access the content to MEC device B viabase station B. In some implementations, MEC device B may obtain one ormore respective requests from the one or more user devices B to accessthe content via base station B.

As shown in FIG. 1C and by reference number 106, MEC device A maydetermine a total number of the one or more user devices A. For example,MEC device A may determine a total number of the requests to access thecontent that MEC device A obtained from the one or more user devices Ato determine the total number of the one or more user devices A. Asshown by reference number 108, MEC device A may determine a thresholdnumber of user devices. For example, MEC device A may determine acontent hosting requirement of MEC device A and may determine thethreshold based on the content hosting requirement of MEC device A. Thecontent hosting requirement may indicate when MEC device A can hostmulticast or broadcast content. For example, the content hostingrequirement may be a multicast or broadcast hosting efficiencyrequirement that defines when sending content to multiple user devicesas a multicast or broadcast transmission is more suitable (e.g., basedon consumption of processing resources, memory resources, powerresources, networking resources, and/or the like of MEC device A) thansending the content to the multiple user devices as individual unicasttransmissions.

As shown in FIG. 1D and by reference number 110, MEC device A maydetermine that the total number of the one or more user devices Asatisfies the threshold (e.g., the total number of the one or more userdevices A is greater than or equal to the threshold). In someimplementations, MEC device A may send, based on determining that thetotal number of the one or more user devices A satisfies the threshold,a message to one or more other MEC devices indicating that MEC device Ais multicast or broadcast enabled (e.g., a message indicating that MECdevice A can send the content to the one or more user devices A as amulticast or broadcast transmission). For example, MEC device A may sendthe message to MEC device B, MEC device C, and/or MEC device D.

As shown by reference number 112, MEC device A may determine a latencyrequirement associated with the content. The latency requirement maydepend on the type of the content. For example, time synchronizedcontent may have a first latency requirement (e.g., latency needs to beless than about 10 milliseconds). As another example, live streamingvideo content may have a second latency requirement (e.g., latency canbe greater than or equal to about 10 milliseconds but needs to be lessthan about 500 milliseconds). In another example, public safety contentmay have a third latency requirement (e.g., latency can be greater thanor equal to about 500 milliseconds, but needs to be less than about1,000 milliseconds). The latency requirement may indicate a desiredlatency range defined by a lower latency value and/or an upper latencyvalue (e.g., where the desired latency range is greater than or equal tothe lower latency value and less than the upper latency value). Forexample, the first latency requirement may have a lower latency value of0 and/or an upper latency value of about 10 milliseconds; the secondlatency requirement may have a lower latency value of about 10milliseconds and/or an upper latency value of about 500 milliseconds;the third latency requirement may have a lower latency value of about500 milliseconds and/or an upper latency value of about 1,000milliseconds, and/or the like. In some implementations, MEC device A maydetermine the type of the content (e.g., by processing the content) andmay determine, based on the type of the content, the latencyrequirement.

As shown in FIG. 1E and by reference number 114, MEC device A maydetermine whether MEC device A can satisfy the latency requirement. Forexample, MEC device A may determine whether MEC device A can send thecontent to the one or more user devices A such that the latencyassociated with sending the content to the one or more user devices A isgreater than or equal to the lower latency value of the latencyrequirement and/or less than the upper latency value of the latencyrequirement. In some implementations, MEC device A can determine alatency capability of MEC device A and determine, based on the latencycapability of MEC device A, whether MEC device A can satisfy the latencyrequirement. The latency capability may be based on a physical distancebetween MEC device A and base station A and/or the one or more userdevices A. For example, the latency capability may indicate an estimatedamount of time (or an estimated amount of time range) for the content totravel the distance to base station A and/or the one or more userdevices A (e.g., an estimated amount of time for MEC device A to sendthe content to base station A and/or the one or more user devices A).

As shown by reference number 116, MEC device A may determine that MECdevice A can satisfy the latency requirement. For example, MEC device Amay determine that the latency capability of MEC device A is greaterthan or equal to the lower latency value of the latency requirementand/or less than the upper latency value of the latency requirement andthat therefore MEC device A can satisfy the latency requirement.

As shown by reference number 118, MEC device A can cause MEC device A tosend the content to the one or more user devices A. For example, MECdevice A can cause MEC device A to host the content and/or send thecontent (e.g., as a multicast or broadcast transmission) to the one ormore user devices A when MEC device A can satisfy the latencyrequirement. MEC device A may send the content to the one or more userdevices A via base station A. As shown by reference number 120, the oneor more user devices A may receive the content from MEC device A viabase station A.

Additionally, or alternatively, MEC device A may determine that MECdevice A cannot satisfy the latency requirement. For example, MEC deviceA may determine that the latency capability of MEC device A is less thanthe lower latency value of the latency requirement and that thereforeMEC device A cannot satisfy the latency requirement.

Accordingly, as shown in FIG. 1F and by reference number 122, MEC deviceA may determine whether MEC device C can satisfy the latencyrequirement. For example, MEC device A may determine a latencycapability of MEC device C (e.g., by communicating with MEC device C)and may determine, based on the latency capability of MEC device C,whether MEC device C can satisfy the latency requirement in a similarmanner as described herein in relation to MEC device A.

As shown by reference number 124, MEC device A may determine that MECdevice C can satisfy the latency requirement. For example, MEC device Amay determine that the latency capability of MEC device C is greaterthan or equal to the lower latency value of the latency requirementand/or less than the upper latency value of the latency requirement andthat therefore MEC device C can satisfy the latency requirement.

As shown by reference number 126, MEC device A may cause MEC device C tosend the content to the one or more user devices A. For example, MECdevice A may cause MEC device C (e.g., by sending a message to MECdevice C) to host the content and/or send the content (e.g., as amulticast or broadcast transmission) to the one or more user devices Awhen MEC device C can satisfy the latency requirement. MEC device C maysend the content to the one or more user devices A via base station A.As shown by reference number 128, the one or more user devices A mayreceive the content from MEC device C via base station A.

Additionally, or alternatively, MEC device A may determine that MECdevice C cannot satisfy the latency requirement. For example, MEC deviceA may determine that the latency capability of MEC device C is less thanthe lower latency value of the latency requirement and/or that thelatency capability of MEC device C is greater than the upper latencyvalue of the requirement and that therefore MEC device C cannot satisfythe latency requirement.

Accordingly, as shown in FIG. 1G and by reference number 130, MEC deviceA may determine that MEC device A and/or MEC device C cannot satisfy thelatency requirement. As shown by reference number 132, MEC device A cancause MEC device D to send the content to the one or more user devicesA. For example, MEC device A can cause MEC device D (e.g., by sending amessage to MEC device D) to host the content and/or send the content tothe one or more user devices A (e.g., as a multicast or broadcasttransmission) when MEC device A and/or MEC device C cannot satisfy thelatency requirement. MEC device D may send the content to the one ormore user devices A via base station A. As shown by reference number134, the one or more user devices A may receive the content from MECdevice D via base station A.

While some implementations described herein concern MEC device Adetermining a latency requirement and determining whether MEC device Aand/or MEC device C can satisfy the latency requirement, additionalimplementations are contemplated concerning other requirements. Forexample, MEC device A may determine a resource requirement (e.g., anamount of processing resources, memory resources, power resources,networking resources, and/or the like) for hosting content. MEC device Amay determine whether MEC device A and/or MEC device C can satisfy theresource requirement (e.g., determine whether MEC device A and/or MECdevice C each have enough available processing resources, memoryresources, power resources, networking resources, and/or the like) tohost the content using a similar process as described herein in relationto FIGS. 1E and 1F. Accordingly, based on determining whether MEC deviceA and/or MEC device C can satisfy the resource requirement, MEC device Amay cause MEC device A, MEC device C, or MEC device D to host thecontent using a similar process as described herein in relation to FIGS.1E, 1F, and 1G.

Additionally, or alternatively, as shown in FIG. 1H and reference number136, MEC device A may obtain information about user devices B requestingthe content. For example, MEC device A may obtain the information fromMEC device B (e.g., MEC device B may send the information to MEC deviceA, MEC device A may query MEC device B for the information, and/or thelike). MEC device A may obtain the information after MEC device Adetermines that MEC device A cannot satisfy the latency requirement.

In some implementations, after obtaining the information, MEC device Amay determine a total number of the one or more user devices B. Forexample, MEC device A may process the information to determine the totalnumber of the one or more user devices B. In some implementations, MECdevice A may determine whether the total number of the one or more userdevices B satisfies the threshold (e.g., whether the total number of theone or more user devices B is greater than or equal to the threshold).

As shown in FIG. 1I and by reference number 138, MEC device A maydetermine that the total number of one or more user devices B does notsatisfy the threshold (e.g., the total number of the one or more userdevices B is less than the threshold). As shown by reference number 140,MEC device A, based on determining that the total number of one or moreuser devices B does not satisfy the threshold, may cause MEC device A tosend the content to the one or more user devices A. For example, MECdevice A may send the content (e.g., as a multicast or broadcasttransmission) to the one or more user devices A via base station A. Asshown by reference number 142, the one or more user devices A mayreceive the content from MEC device A via base station A.

Additionally, or alternatively, as shown in FIG. 1J and by referencenumber 144, MEC device A may determine that the total number of one ormore user devices B satisfies the threshold (e.g., the total number ofthe one or more user devices B is greater than or equal to thethreshold). As shown by reference number 146, MEC device A, based ondetermining that the total number of one or more user devices Bsatisfies the threshold, may cause MEC device C or MEC device D to sendthe content (e.g., as a multicast or broadcast transmission) to the oneor more user devices A and/or the one or more user devices B. Forexample, in a similar manner as described herein in relation to FIG. 1F,MEC device A may determine a latency capability of MEC device C (e.g.,by communicating with MEC device C) and may determine, based on thelatency capability of MEC device C, whether MEC device C can satisfy thelatency requirement. In some implementations, when MEC device A maydetermine that MEC device C can satisfy the latency requirement, MECdevice A may cause MEC device C to send the content (e.g., as amulticast or broadcast transmission) to the one or more user devices Aand/or the one or more user devices B. In some implementations, when MECdevice A may determine that MEC device C cannot satisfy the latencyrequirement, MEC device A may cause MEC device D to send the content(e.g., as a multicast or broadcast transmission) to the one or more userdevices A and/or the one or more user devices B.

MEC device C and/or MEC device D may send the content to the one or moreuser devices A via base station A. Additionally, or alternatively, MECdevice C and/or MEC device D may send the content to the one or moreuser devices B via base station B. As shown by reference number 148, theone or more user devices A may receive the content from MEC device Cand/or MEC device D via base station A. As shown by reference number150, the one or more user devices B may receive the content from MECdevice C and/or MEC device D via base station B.

The number and arrangement of devices and networks shown in FIG. 1 areprovided as one or more examples. In practice, there may be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan those shown in FIG. 1. Furthermore, two or more devices shown inFIG. 1 may be implemented within a single device, or a single deviceshown in FIG. 1 may be implemented as multiple, distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) of example implementation 100 may perform one or more functionsdescribed as being performed by another set of devices of exampleimplementation 100.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,environment 200 may include a user device 210, a user device 220, a basestation 230, a base station 240, a MEC device 250, a MEC device 260, aMEC device 270, a MEC device 280, and/or a network 290. Devices ofenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections. Someimplementations may be performed in association with a wirelesscommunication network, such as a third generation (3G) network, a longterm evolution (LTE) network, a fifth generation (5G) network, and/orthe like.

Environment 200 may include one or more far edge clouds, an edge cloud,and/or a central cloud. A cloud may represent a computing environmentwhere a MEC device associated with the cloud may provide services (e.g.,deploy applications, store and process content, and or the like) for oneor more user devices. A cloud may be associated with an area thatencompasses a base station and a MEC device. For example, a far edgecloud may be associated with an area around a base station (e.g., basestation 230 and/or base station 240) and/or a MEC device (e.g., MECdevice 250 and/or MEC device 260) where the base station and the MECdevice are physically near each other. As another example, the centralcloud may be associated with an area around a base station (e.g., basestation 230 and/or base station 240) and/or a MEC device (e.g. MECdevice 280) where the base station and MEC device are physically farfrom each other. In another example, the edge cloud may be associatedwith an area around a base station (e.g., base station 230 and/or basestation 240) and/or a MEC device (e.g. MEC device 270) where the MECdevice is physically farther from the base station than the MEC deviceassociated with the far edge cloud and the MEC device is physicallynearer the base station than the MEC device associated with the centralcloud.

In some implementations, a first far edge cloud may be associated withbase station 230 and/or MEC device 250. A second far edge cloud may beassociated with base station 240 and/or MEC device 260. The edge cloudmay be associated with base station 230, base station 240, and/or MECdevice 270. The central cloud may be associated with base station 230,base station 240, and/or MEC device 280.

User devices 210 include one or more devices capable of communicatingwith base station 230, a MEC device (e.g., MEC device 250, MEC device270, and/or MEC device 280), and/or a network (e.g., network 290). Forexample, a user device 210 may include a wireless communication device,a radiotelephone, a personal communications system (PCS) terminal (e.g.,that may combine a cellular radiotelephone with data processing and datacommunications capabilities), a smart phone, a laptop computer, a tabletcomputer, a personal gaming system, user equipment, and/or a similardevice. User device 210 may be capable of communicating using uplink(e.g., user device to base station) communications, downlink (e.g., basestation to user device) communications, and/or side link (e.g., userdevice to user device) communications.

User devices 220 include one or more devices capable of communicatingwith base station 240, a MEC device (e.g., MEC device 260, MEC device270, and/or MEC device 280), and/or a network (e.g., network 290). Forexample, a user device 220 may include a wireless communication device,a radiotelephone, a personal communications system (PCS) terminal (e.g.,that may combine a cellular radiotelephone with data processing and datacommunications capabilities), a smart phone, a laptop computer, a tabletcomputer, a personal gaming system, user equipment, and/or a similardevice. User device 220 may be capable of communicating using uplink(e.g., user device to base station) communications, downlink (e.g., basestation to user device) communications, and/or side link (e.g., userdevice to user device) communications.

Base station 230 includes one or more devices capable of communicatingwith one or more user devices 210 using a cellular Radio AccessTechnology (RAT). For example, base station 230 may include a basetransceiver station, a radio base station, a node B, an evolved node B(eNB), a gNB, a base station subsystem, a cellular site, a cellulartower (e.g., a cell phone tower, a mobile phone tower, etc.), an accesspoint, a transmit receive point (TRP), a radio access node, a macrocellbase station, a microcell base station, a picocell base station, afemtocell base station, or a similar type of device. Base station 230may transfer traffic between a user device 210 (e.g., using a cellularRAT), a MEC device (e.g., MEC device 250, MEC device 270, MEC device280, and/or the like), and/or network 290. Base station 230 may provideone or more cells that cover geographic areas. Base station 230 may be amobile base station. Base station 230 may be capable of communicatingusing multiple RATs.

Base station 240 includes one or more devices capable of communicatingwith one or more user devices 220 using a cellular Radio AccessTechnology (RAT). For example, base station 240 may include a basetransceiver station, a radio base station, a node B, an evolved node B(eNB), a gNB, a base station subsystem, a cellular site, a cellulartower (e.g., a cell phone tower, a mobile phone tower, etc.), an accesspoint, a transmit receive point (TRP), a radio access node, a macrocellbase station, a microcell base station, a picocell base station, afemtocell base station, or a similar type of device. Base station 240may transfer traffic between a user device 220 (e.g., using a cellularRAT), a MEC device (e.g., MEC device 260, MEC device 270, MEC device280, and/or the like), and/or network 290. Base station 240 may provideone or more cells that cover geographic areas. Base station 240 may be amobile base station. Base station 240 may be capable of communicatingusing multiple RATs.

MEC device 250 includes one or more devices capable of hosting and/orsending content to user devices 210. For example, MEC device 250 mayinclude a server device, a group of server devices, a desktop computer,a laptop computer, a multicast and broadcast function device (MCBC),and/or a similar type of device. In some implementations, MEC device 250may selectively cause MEC device 250, MEC device 270, and/or MEC device280 to send content to user devices 210 and/or user devices 220. In someimplementations, MEC device 250 may be hosted as part of base station230 or at a site associated with base station 230. In someimplementations, MEC device 250 may be hosted within a far edge cloud.

MEC device 260 includes one or more devices capable of hosting and/orsending content to user devices 220. For example, MEC device 260 mayinclude a server device, a group of server devices, a desktop computer,a laptop computer, a multicast and broadcast function device (MCBC),and/or a similar type of device. In some implementations, MEC device 260may send information related to user devices 220 requesting access tothe content. In some implementations, MEC device 260 may be hosted aspart of base station 240 or at a site associated with base station 240.In some implementations, MEC device 260 may be hosted within a far edgecloud.

MEC device 270 includes one or more devices capable of hosting and/orsending content to user devices 210 and/or user devices 220. Forexample, MEC device 270 may include a server device, a group of serverdevices, a desktop computer, a laptop computer, a multicast andbroadcast function device (MCBC), and/or a similar type of device. Insome implementations, MEC device 250 may cause MEC device 270 to sendcontent to user devices 210 and/or user devices 220. In someimplementations, MEC device 270 may be hosted within an edge cloud.

MEC device 280 includes one or more devices capable of hosting and/orsending content to user devices 210 and/or user devices 220. Forexample, MEC device 280 may include a server device, a group of serverdevices, a desktop computer, a laptop computer, a multicast andbroadcast function device (MCBC), and/or a similar type of device. Insome implementations, MEC device 250 may cause MEC device 280 to sendcontent to user devices 210 and/or user devices 220. In someimplementations, MEC device 280 may be hosted within a central cloud.

Network 290 includes one or more wired and/or wireless networks. Forexample, network 290 can include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, a corenetwork, and/or the like, and/or a combination of these or other typesof networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as one or more examples. In practice, there may be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan those shown in FIG. 2. Furthermore, two or more devices shown inFIG. 2 may be implemented within a single device, or a single deviceshown in FIG. 2 may be implemented as multiple, distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) of environment 200 may perform one or more functions describedas being performed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user devices 210, user devices 220, base station 230,base station 240, MEC device 250, MEC device 260, MEC device 270, and/orMEC device 280. In some implementations user devices 210, user devices220, base station 230, base station 240, MEC device 250, MEC device 260,MEC device 270, and/or MEC device 280 may include one or more devices300 and/or one or more components of device 300. As shown in FIG. 3,device 300 may include a bus 310, a processor 320, a memory 330, astorage component 340, an input component 350, an output component 360,and a communication interface 370.

Bus 310 includes a component that permits communication among multiplecomponents of device 300. Processor 320 is implemented in hardware,firmware, and/or a combination of hardware and software. Processor 320is a central processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, and/or amagneto-optic disk), a solid state drive (SSD), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 360 includes a component thatprovides output information from device 300 (via, e.g., a display, aspeaker, a haptic feedback component, an audio or visual indicator,and/or the like).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver, a separate receiver, a separate transmitter, and/or thelike) that enables device 300 to communicate with other devices, such asvia a wired connection, a wireless connection, or a combination of wiredand wireless connections. Communication interface 370 may permit device300 to receive information from another device and/or provideinformation to another device. For example, communication interface 370may include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a wireless local area networkinterface, a cellular network interface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. As used herein,the term “computer-readable medium” refers to a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardware circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for facilitatingdelivery of multicast or broadcast content in a multi-access edgecomputing (MEC) environment. In some implementations, one or moreprocess blocks of FIG. 4 may be performed by an edge device (e.g., MECdevice 250). In some implementations, one or more process blocks of FIG.4 may be performed by another device or a group of devices separate fromor including the edge device, such as a user device (e.g., user device210 and/or user device 220), a base station (e.g., base station 230and/or base station 240), another edge device (e.g., MEC device 260, MECdevice 270, and/or MEC device 280), and/or the like.

As shown in FIG. 4, process 400 may include obtaining, via a basestation, one or more respective requests from one or more user devicesto access content (block 405). For example, the edge device (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370 and/or the like) mayobtain, via a base station, one or more respective requests from one ormore user devices to access content, as described above. The content maybe multicast content, broadcast content, time synchronized content,and/or the like.

As further shown in FIG. 4, process 400 may include determining a totalnumber of the one or more user devices (block 410). For example, theedge device (e.g., using processor 320, memory 330, storage component340, input component 350, output component 360, communication interface370 and/or the like) may determine a total number of the one or moreuser devices, as described above.

As further shown in FIG. 4, process 400 may include determining that thetotal number of the one or more user devices satisfies a threshold(block 415). For example, the edge device (e.g., using processor 320,memory 330, storage component 340, input component 350, output component360, communication interface 370 and/or the like) may determine that thetotal number of the one or more user devices satisfies a threshold, asdescribed above. The edge device may send, based on determining that thetotal number of the one or more user devices satisfies the threshold, amessage to a first different edge device or a second different edgedevice indicating that the edge device is multicast or broadcastenabled. In some implementations, the edge device may determine amulticast or broadcast hosting efficiency requirement of the edge deviceand may determine the threshold based on the multicast or broadcasthosting efficiency requirement of the edge device.

As further shown in FIG. 4, process 400 may include determining, basedon the total number of the one or more user devices satisfying thethreshold, a latency requirement associated with the content (block420). For example, the edge device (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370 and/or the like) may determine, based on thetotal number of the one or more user devices satisfying the threshold, alatency requirement associated with the content, as described above. Insome implementations, the edge device may determine a type of thecontent and determine, based on the type of the content, the latencyrequirement.

As further shown in FIG. 4, process 400 may include determining whetherthe edge device or a first different edge device can satisfy the latencyrequirement (block 425). For example, the edge device (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370 and/or the like) maydetermine whether the edge device or a first different edge device cansatisfy the latency requirement, as described above. As another example,the edge device may determine a latency capability of the edge deviceand may determine, based on the latency capability of the edge device,that the edge device can or cannot satisfy the latency requirement. Inanother example, the edge device may determine, based on the latencycapability of the edge device, that the edge device cannot satisfy thelatency requirement; may determine, based on determining that the edgedevice cannot satisfy the latency requirement, a latency capability ofthe first different edge device; and may determine, based on the latencycapability of the first different edge device, that the different firstedge device can or cannot satisfy the latency requirement.

As further shown in FIG. 4, process 400 may include selectively causing,based on determining whether the edge device or the first different edgedevice can satisfy the latency requirement, the edge device, the firstdifferent edge device, or a second different edge device to send thecontent to the one or more user devices via the base station (block430). For example, the edge device (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370 and/or the like) may selectively cause,based on determining whether the edge device or the first different edgedevice can satisfy the latency requirement, the edge device, the firstdifferent edge device, or a second different edge device to send thecontent to the one or more user devices via the base station, asdescribed above. For example, the edge device may be caused to send thecontent to the one or more user devices when the edge device can satisfythe latency requirement; the first different edge device may be causedto send the content to the one or more user devices when the firstdifferent edge device can satisfy the latency requirement; or the seconddifferent edge device may be caused to send the content to the one ormore user devices when the edge device and the first different edgedevice cannot satisfy the latency requirement.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the edge device may be associated with a firstfar edge cloud, the first different edge device may be associated withan edge cloud, and the second different edge device may be associatedwith a central cloud. The base station may be associated with the firstfar edge cloud, the edge cloud, and the central cloud and/or thedifferent base station may be associated with a second far edge cloud,the edge cloud, and the central cloud. The base station may beassociated with the edge device, the first different edge device, andthe second different edge device. The different base station may beassociated with the first different edge device and the second differentedge device.

In some implementations, after determining that the edge device cannotsatisfy the latency requirement, the edge device may obtain informationrelated to one or more different user devices requesting access to thecontent, wherein the one or more different user devices are associatedwith a different base station. The edge device may determine a totalnumber of the one or more different user devices and may determinewhether the total number of the one or more different user devicessatisfies the threshold. The edge device may selectively cause, based ondetermining whether the total number of the one or more different userdevices satisfies the threshold, the edge device, the first differentedge device, or the second different edge device to send the content tothe one or more user devices via the base station.

For example, the edge device may cause, based on the total number of theone or more different user devices not satisfying the threshold, theedge device to send the content to the one or more user devices. Asanother example, the edge device may determine, based on determiningthat the total number of the one or more different user devicessatisfies the threshold, a latency capability of the first differentedge device and may determine, based on the latency capability of thefirst different edge device, whether the first different edge device cansatisfy the latency requirement. The edge device may cause, based ondetermining that the first different edge device can satisfy the latencyrequirement, the first different edge device to send the content to theone or more user devices. Additionally, or alternatively, the edgedevice may cause, based on determining that the first different edgedevice cannot satisfy the latency requirement, the second different edgedevice to send the content to the one or more user devices.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc., depending on the context.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: obtaining, by an edgedevice and via a base station, one or more respective requests from oneor more user devices to access content; determining, by the edge device,a total number of the one or more user devices; determining, by the edgedevice, that the total number of the one or more user devices satisfiesa threshold; determining, by the edge device and based on the totalnumber of the one or more user devices satisfying the threshold, alatency requirement associated with the content; determining, by theedge device, whether the edge device can satisfy the latencyrequirement; obtaining, by the edge device, information related to oneor more different user devices requesting access to the content, whereinthe one or more different user devices are associated with a differentbase station; determining, by the edge device, a total number of the oneor more different user devices; determining, by the edge device, whetherthe total number of the one or more different user devices satisfies thethreshold; and selectively causing, by the edge device and based ondetermining whether the edge device can satisfy the latency requirementand based on determining whether the total number of the one or moredifferent user devices satisfies the threshold, the edge device or adifferent edge device to send the content to the one or more userdevices via the base station, wherein the edge device is caused to sendthe content to the one or more user devices when the edge device cansatisfy the latency requirement, or wherein a first different edgedevice or a second different edge device is caused to send the contentto the one or more user devices when the edge device cannot satisfy thelatency requirement, wherein the base station is associated with a firstfar edge cloud, an edge cloud, and a central cloud, wherein thedifferent base station is associated with a second far edge cloud, theedge cloud, and the central cloud, wherein the edge device is associatedwith the first far edge cloud, wherein the first different edge deviceis associated with the edge cloud, and wherein the second different edgedevice is associated with the central cloud.
 2. The method of claim 1,wherein the content is multicast content or broadcast content.
 3. Themethod of claim 1, wherein determining the latency requirementassociated with the content comprises: determining a type of thecontent; and determining, based on the type of the content, the latencyrequirement.
 4. The method of claim 1, wherein determining whether theedge device can satisfy the latency requirement comprises: determining alatency capability of the edge device; and determining, based on thelatency capability of the edge device, that the edge device can satisfythe latency requirement.
 5. The method of claim 1, wherein determiningwhether the edge device can satisfy the latency requirement comprises:determining a latency capability of the edge device; determining, basedon the latency capability of the edge device, that the edge devicecannot satisfy the latency requirement; determining, based ondetermining that the edge device cannot satisfy the latency requirement,a latency capability of the different edge device; and determining,based on the latency capability of the different edge device, that thedifferent edge device can satisfy the latency requirement.
 6. The methodof claim 1, further comprising: determining that the content is livestreaming video content or public safety content; and whereindetermining the latency requirement associated with the contentcomprises: determining a live streaming video content latencyrequirement associated with the live streaming video content and apublic safety content latency requirement associated with the publicsafety content, wherein the live streaming video content latencyrequirement is different from the public safety content latencyrequirement.
 7. An edge device, comprising: one or more memories; andone or more processors, communicatively coupled to the one or morememories, to: obtain, via a base station, one or more respectiverequests from one or more user devices to access content; determine atotal number of the one or more user devices; determine that the totalnumber of the one or more user devices satisfies a threshold; determine,based on the total number of the one or more user devices satisfying thethreshold, a latency requirement associated with the content; determinewhether the edge device or a first different edge device can satisfy thelatency requirement; obtain information related to one or more differentuser devices requesting access to the content, wherein the one or moredifferent user devices are associated with a different base station;determine a total number of the one or more different user devices;determine whether the total number of the one or more different userdevices satisfies the threshold; and selectively cause, based ondetermining whether the edge device or the first different edge devicecan satisfy the latency requirement and based on determining whether thetotal number of the one or more different user devices satisfies thethreshold, the edge device, the first different edge device, or a seconddifferent edge device to send the content to the one or more userdevices via the base station, wherein the edge device is caused to sendthe content to the one or more user devices when the edge device cansatisfy the latency requirement, wherein the first different edge deviceis caused to send the content to the one or more user devices when thefirst different edge device can satisfy the latency requirement, orwherein the second different edge device is caused to send the contentto the one or more user devices when the edge device and the firstdifferent edge device cannot satisfy the latency requirement, whereinthe base station is associated with a first far edge cloud, an edgecloud, and a central cloud, wherein the different base station isassociated with a second far edge cloud, the edge cloud, and the centralcloud, wherein the edge device is associated with the first far edgecloud, wherein the first different edge device is associated with theedge cloud, and wherein the second different edge device is associatedwith the central cloud.
 8. The edge device of claim 7, wherein thecontent is time synchronized content.
 9. The edge device of claim 7,wherein the one or more processors are further to: determine a multicastor broadcast hosting efficiency requirement of the edge device; anddetermine the threshold based on the multicast or broadcast hostingefficiency requirement of the edge device.
 10. The edge device of claim7, wherein the one or more processors, when determining that the totalnumber of the one or more user devices satisfies the threshold, are to:send a message to the first different edge device or the seconddifferent edge device indicating that the edge device is multicast orbroadcast enabled.
 11. The edge device of claim 7, wherein the one ormore processors, when determining whether the edge device or the firstdifferent edge device can satisfy the latency requirement, are to:determine a latency capability of the edge device; and determine, basedon the latency capability of the edge device, that the edge device cansatisfy the latency requirement.
 12. The edge device of claim 7, whereinthe one or more processors, when determining whether the edge device orthe first different edge device can satisfy the latency requirement, areto: determine a latency capability of the edge device; determine, basedon the latency capability of the edge device, that the edge devicecannot satisfy the latency requirement; determine, based on determiningthat the edge device cannot satisfy the latency requirement, a latencycapability of the first different edge device; and determine, based onthe latency capability of the first different edge device, that thefirst different edge device can satisfy the latency requirement.
 13. Theedge device of claim 7, wherein the one or more processors, whendetermining whether the edge device or the first different edge devicecan satisfy the latency requirement, are to: determine a latencycapability of the edge device; determine, based on the latencycapability of the edge device, that the edge device cannot satisfy thelatency requirement; determine, based on determining that the edgedevice cannot satisfy the latency requirement, a latency capability ofthe first different edge device; and determine, based on the latencycapability of the first different edge device, that the first differentedge device cannot satisfy the latency requirement.
 14. The edge deviceof claim 7, wherein the one or more processors are further to: determinethat the content is live streaming video content or public safetycontent; and wherein the one or more processors, when determining thelatency requirement associated with the content, are to: determine alive streaming video content latency requirement associated with thelive streaming video content and a public safety content latencyrequirement associated with the public safety content, wherein the livestreaming video content latency requirement is different from the publicsafety content latency requirement.
 15. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors of an edge device, cause the one or more processors to:obtain, via a base station, one or more respective requests from one ormore user devices to access content; determine a total number of the oneor more user devices; determine that the total number of the one or moreuser devices satisfies a threshold; determine that the edge devicecannot satisfy a latency requirement associated with the content; obtaininformation related to one or more different user devices requestingaccess to the content, wherein the one or more different user devicesare associated with a different base station; determine a total numberof the one or more different user devices; determine whether the totalnumber of the one or more different user devices satisfies thethreshold; and selectively cause, based on determining whether the totalnumber of the one or more different user devices satisfies thethreshold, the edge device, a first different edge device, or a seconddifferent edge device to send the content to the one or more userdevices via the base station, wherein: the base station is associatedwith a first far edge cloud, an edge cloud, and a central cloud, thedifferent base station is associated with a second far edge cloud, theedge cloud, and the central cloud, the edge device is associated withthe first far edge cloud, the first different edge device is associatedwith the edge cloud, and the second different edge device is associatedwith the central cloud.
 16. The non-transitory computer-readable mediumof claim 15, wherein: the base station is associated with the edgedevice, the first different edge device, and the second different edgedevice; and the different base station is associated with the firstdifferent edge device and the second different edge device.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the one ormore instructions, that cause the one or more processors to determinewhether the total number of the one or more different user devicessatisfies the threshold, cause the one or more processors to: determinethat the total number of the one or more different user devices does notsatisfy the threshold, wherein the one or more instructions, that causethe one or more processors to selectively cause the edge device, thefirst different edge device, or the second different edge device to sendthe content to the one or more user devices via the base station, causethe one or more processors to: cause, based on the total number of theone or more different user devices not satisfying the threshold, theedge device to send the content to the one or more user devices.
 18. Thenon-transitory computer-readable medium of claim 15, wherein the one ormore instructions, that cause the one or more processors to determinewhether the total number of the one or more different user devicessatisfies the threshold, cause the one or more processors to: determinethat the total number of the one or more different user devicessatisfies the threshold, wherein the one or more instructions, thatcause the one or more processors to selectively cause the edge device,the first different edge device, or the second different edge device tosend the content to the one or more user devices via the base station,cause the one or more processors to: determine, based on determiningthat the total number of the one or more different user devicessatisfies the threshold, a latency capability of the first differentedge device; determine, based on the latency capability of the firstdifferent edge device, that the first different edge device can satisfythe latency requirement; and cause, based on determining that the firstdifferent edge device can satisfy the latency requirement, the firstdifferent edge device to send the content to the one or more userdevices.
 19. The non-transitory computer-readable medium of claim 15,wherein the one or more instructions, that cause the one or moreprocessors to determine whether the total number of the one or moredifferent user devices satisfies the threshold, cause the one or moreprocessors to: determine that the total number of the one or moredifferent user devices satisfies the threshold, wherein the one or moreinstructions, that cause the one or more processors to selectively causethe edge device, the first different edge device, or the seconddifferent edge device to send the content to the one or more userdevices via the base station, cause the one or more processors to:determine, based on determining that the total number of the one or moredifferent user devices satisfies the threshold, a latency capability ofthe first different edge device; determine, based on the latencycapability of the first different edge device, that the first differentedge device cannot satisfy the latency requirement; and cause, based ondetermining that the first different edge device cannot satisfy thelatency requirement, the second different edge device to send thecontent to the one or more user devices.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: determine that the content is livestreaming video content or public safety content; and wherein the one ormore instructions, that cause the one or more processors to determinethat the content is live streaming video content or public safetycontent, cause the one or more processors to: determine a live streamingvideo content latency requirement associated with the live streamingvideo content and a public safety content latency requirement associatedwith the public safety content, wherein the live streaming video contentlatency requirement is different from the public safety content latencyrequirement.